System and method for labeling maps

ABSTRACT

A system and method for label placement is disclosed that achieves the twin goals of practical efficiency and high labeling quality by employing cartographic heuristics. A caller defines map and label properties. Then labels are pulled within a map boundary. Labels are next ordered by priority in descending importance. The order of testing labels is determined. Attempts are made to move overlapping labels. This is an iterative process; therefore there must be criteria that halt the procedure. Upon reaching an acceptable solution, the label properties are adjusted to reflect the new label placements.

REFERENCE TO RELATED APPLICATION

This application is a continuation of Ser. No. 10/462,044 filed Jun. 16,2003.

FIELD OF THE INVENTION

The present invention relates to a computer-implemented method andapparatus for automatically labeling maps or graph layouts in accordancewith predefined label criteria.

BACKGROUND OF THE INVENTION

Maps include geographic drawings showing countries, cities, rivers,bodies of water, mountains, and other features of interest. Labelingcartographic features is a fundamental part of map-making. Placing eachlabel optimally with respect to its corresponding feature invariablyproduces labels overlapping each other or too close to each other. Asthis results in confusion and unacceptable maps, methods to repositionlabels or not draw them at all must be used to create a map that conveysas much information as possible.

Tagging graphical objects with text labels is a fundamental task in thedesign of many types of informational graphics. This problem is seen inits most essential form in cartography, but it also arises frequently inthe production of other informational graphics such as scatter plots.The quality of a labeling is determined essentially by the degree towhich labels obscure other labels or features of the underlying graphic.The goal is to choose positions for the labels that do not give rise tolabel overlaps and that minimize obscuration of features. Constructionof a good labeling is thus a combinatorial optimization problem, whichhas been shown to be NP-hard (Marks and Shieber, 1991). As ahypothetical baseline algorithm, randomly choosing positions for eachlabel generates a poor labeling, both aesthetically, and as quantifiedusing a metric that counts the number of conflicted labels, i.e., thosethat obscure point features or other labels.

In addition to geographical and technical maps, there are many labelingapplications relating to graph layouts and drawings. These applicationsinclude, but are not limited to, areas such as database design (e.g.entity relationship diagrams), software engineering including CASE,software debugging, complex web pages, CAD drafting, complex electricaldiagrams, and telecommunications and communications networking. In fact,the labeling of the graphical features of any drawing is generallynecessary because it conveys information essential to understanding thedrawing. For complex and information rich drawings, computer aidedlabeling is increasingly employed.

As used in the present specification, the term “map” is used to includeboth geographical and technical maps as well as graph layouts anddrawings. The term “label” is used to refer to text or other indicia tobe placed on a map.

A system and method for labeling objects on maps while avoidingcollisions with other labels has been sought after. Some apparentlypowerful algorithms for automatic label placement on maps use heuristicsthat capture considerable cartographic expertise but are hampered byprovably inefficient methods of search and optimization.

This patent discloses a system and method for label placement thatachieves the twin goals of practical efficiency and high labelingquality by employing cartographic heuristics.

SUMMARY OF THE INVENTION

The present invention provides a computer-implemented system and methodof automatically labeling a map in accordance with predefined labellocation, placement, and priority criteria.

Here, each label is represented as a convex polygon with any orientationon the map. Labels have various parameters associated with them such aslocation, size, shape, number and location of vertices, target feature,priority, movement constraints, and clearance. After finding the bestposition of a label for every feature without regard to other labels orfeatures, higher priority label positions are compared to lower prioritylabel positions two at a time. If the labels interfere, the lowerpriority label is moved within its movement constraint. Severalcandidate locations for the lower priority label position are found bymoving it the shortest distance to avoid the higher priority labelposition. A new location is acceptable if the location does not collidewith a label of higher priority. It can collide with a label of lowerpriority. If no candidate positions are acceptable, the label is notmoved. This process continues until all labels are inspected, afterwhich a deviation from the desired result function is calculated. Thisfunction is zero if the label interference for all labels is zero andgreater than zero otherwise. The whole process is repeated until theevaluation function equals zero or the change in the evaluation functionis less than a given percent (e.g., two percent) for a small number(e.g., four) of iterations or if it oscillates for a number (e.g., six)of iterations or if the number of iterations is greater than a setnumber (e.g., twenty). If any interference remains, then interferinglabels with lower priorities are not drawn.

The details of the present invention, both as to its structure andoperation, can best be understood in reference to the accompanyingdrawings, in which like reference to the accompanying drawings, in whichlike reference numerals refer to like parts, and in which:

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagram of a computer hardware architecture compatible withthe present system and method.

FIG. 2 is a schematic diagram showing an exemplary computer programproduct.

FIG. 3 is a flow chart showing the overall logic of the present systemand method.

FIGS. 4 a, 4 b, and 4 c is a flow chart showing the initialization ofthe anti-collision system and method.

FIG. 5 is a flow chart of the sorting labels by priority.

FIG. 6 is a flow chart showing the initialization of halting criteriavariables.

FIGS. 7 a and 7 b is a flow chart showing the test of whether each labelhas been tested.

FIG. 8 is a flow chart showing the overlap test

FIGS. 9 a, 9 b, and 9 c is a flow chart showing the movement procedure.

FIG. 10 is a flow chart showing the initiation of collision scores andpriority ranges.

FIG. 11 is a flow chart showing the calculation of the evaluationfunction.

FIG. 12 is a flow chart showing the halt routine.

FIG. 13 is a flow chart showing the routine to adjust label properties.

FIG. 14 is a flow chart showing the return to caller.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

Referring initially to FIG. 1, a system is shown which includes adigital processing apparatus. This system is a general-purpose computer1000. The computer may include a graphics display, print hardware, andprint software, or may be as simple as a generic personal computer. Theexample computer in FIG. 1 includes central processor 1010, systemmemory 1015, disk storage 1020 (e.g., hard drive, floppy drive, CD-ROMdrive, or DVD drive), controller 1005, network adapter 1050, videoadapter 1030, and monitor 1055. Data input may be through one or more ofthe following agencies: keyboard 1035, pointing device 1040, diskstorage 1020, local area network 1060, point to point communications1065, and wide area network 1070 (e.g., internet).

One or more features of the computer as shown may be omitted while stillpermitting the practice of the invention. For example, printer 1045 isnot necessary for maps intended to be displayed only on monitor 1055.Likewise, network adapter 1050, local area network 1060, point to pointcommunications 1065, and wide area network 1070 are not necessary whenthe primary method of data input is via removable disk storage.

The flow charts herein illustrate the structure of the logic of thepresent invention as embodied in computer program software. Thoseskilled in the art will appreciate that the flow charts illustrate thestructures of logic elements, such as computer program code elements orelectronic logic circuits, that function according to this invention.Manifestly, the invention is practiced in its essential embodiment by amachine component that renders the logic elements in a form thatinstructs a digital processing apparatus (that is, a computer) toperform a sequence of function steps corresponding to those shown.

FIG. 2 shows a computer program product which includes a disk 1080having a computer usable medium 1085 thereon for storing program modulesa, b, c, and d. While 4 modules are shown in FIG 2, it is to beunderstood that the number of modules into which the program is dividedis arbitrary and may be in any particular embodiment a different number.

Modules a, b, c, d may be a computer program that is executed byprocessor 1010 within the computer 1000 as a series ofcomputer-executable instructions. In addition to the above-mentioneddisk storage 1020, these instructions may reside, for example in RAM orROM of the computer 1000 or the instructions may be stored on a DASDarray, magnetic tape, electronic read-only memory, or other appropriatedata storage device. In an illustrative embodiment of the invention, thecomputer-executable instructions may be lines of compiled C++ code.

FIG. 3 is an overview and summary of the label anti-collision procedurefor maps. The caller of the procedure performs the first stage, routine5, and the second stage, routine 8. Routine 5 involves locating eachlabel on a map in the optimal position with respect to its targetfeature without regard to other labels or features. Routine 8 assignsproperties to the map and the labels.

To begin, the user must specify how to initially place labels on a map.That is, commencing at routine 5, it is assumed that the user willassign positions that give the best label location with respect to itsassociated feature. For this procedure to work, the user places thelabels in the best spots according to their criteria regardless of otherlabels and map features. For example, in the initial positions, labelsmay overlap each other and/or extend over the map boundary. Labels areassumed to be convex polygons while the map boundary is assumed to be arectangle.

Next, at routine 8, the user must assign properties to the map and thelabels. Map properties include its height and width. A label'sproperties include the associated map feature(s), initial location,size, shape, angular orientation, priority, movement constraints, andclearance. In addition, each label has an associated property thatindicates the fraction of the label area that can extend outside the mapboundary before it is not drawn. The procedure takes all of theseproperties into account to move labels to acceptable positions or to notdraw the label.

The following discussion concerns only those geometric objects in theplane of the map, of which the labels are a part. All labels arerestricted to convex planar polygons in this plane. A planar polygon isconvex if it contains all the line segments connecting any pair of itspoints. If two convex planar polygons overlap, this means that:

-   -   1) at least one vertex of one polygon is inside the other        polygon, or    -   2) at least one edge of one polygon crosses or touches (i.e.,        intersects) an edge of the other polygon.

To begin the anti-collision procedure, three initialization steps occur.First, labels lying partially inside the map boundary must either bemoved completely inside the portrait or be excluded from being comparedto other labels and excluded from being drawn. Each label has movementtypes and constraints that determine whether or not the label qualifiesfor movement completely onto the map. These movement types andconstraints are explained below. Labels qualifying for movement to theinside of the map are moved regardless of the collision status with anyother label.

Second, the labels must be ordered in a list with respect to priorityfrom highest priority to lowest priority. In general, many labels willhave the same priority. Within any group of labels with the samepriority, any particular label is randomly placed within that block.

Third and last, variables that monitor the state of the procedure mustbe initialized.

The purpose of routine 10 is to move labels within the map boundary. Iftoo much of a label is outside the boundary, it will not be included inthe map. Each label is tested to determine what fraction of its area iswithin the map boundary.

At routine 20, labels are sorted in order of descending priority.Halting criteria parameters are initialized at routine 30.

Every combination of two labels is tested for overlap in routine 40.When comparing labels to determine if they overlap, it is important tochoose the order of comparison properly to avoid excessive calculationand moving labels more times than necessary. The highest priority labelsshould be tested for overlap before labels of lower priority.

The overlap test at routine 45 has three parts. First, it must bedetermined if any vertex of a first label is inside the second label.Second, it must be determined if any vertex of a second label is insidethe first label. Third, it must determine if any edge of the first labelintersects any edge of the second label. If at any point either label isdetermined to overlap the other label, then any remaining parts arebypassed.

Labels are moved about the map at routine 50 to clear existing labelcollisions. After it is determined that two labels overlap, the routinefinds several new locations for the lower priority of the two labelsthat eradicate the existing overlap. These locations are ranked by howfar the label must be moved, shortest to longest. Then if appropriate,the lower priority is moved to a new location, and its locationparameters are adjusted.

The evaluation function, routine 60, quantifies the extent of labelcollisions. Routines 40, 45, 50, and 60 iterate until halt routinecriteria 70 are satisfied. Labels may move several times before theiterations stop.

After the iterations stop, all labels are examined for any overlap andlabel properties are adjusted at routine 80. Finally, control isreturned at routine 90 to the user to draw or view the map.

FIGS. 4 a, 4 b, and 4 c display the logic of routine 10 in detail. Thepurpose of routine 10 is to make sure all of a label is within the mapboundary. If too much of a label is outside the boundary, it will not beincluded in the map. Each label is tested to determine what fraction ofits area is within the map boundary. A particular label is divided intoa grid; 32 by 32 cells is a typical division that works well inpractice. If the centroid of a cell is within the map boundary, theentire cell contributes to the fraction of the label within theboundary. The areas of each cell within the map are added to together.If this sum of cell areas, divided by the total label area, is greaterthan a predetermined value, then the label is moved entirely onto themap according to the movement procedure and the movement constraintsdescribed below. The only change to the procedure is that there is notest for overlap with other labels. The qualifying labels are moved ontothe map at this time and tested later.

Step 100 obtains a list of labels from data storage. Each label istested for whether the entire label is inside the map boundary. First,step 108 initializes flags that will be used in routine 10. Step 112tests whether vertices of each label are outside the map boundary. Ifthe vertices of a label are all inside the map boundary, then the nextlabel is tested. If any vertices of a label are outside the mapboundary, then, at step 116, a circumscribing rectangle is placed aroundthe label. Then the circumscribing rectangle is divided into a pluralityof cells at step 120. For example, the rectangle may be divided into 64cells by 64 cells forming a total of 4096 cells.

Each cell is tested, step 124. The test includes finding the centerpoint of each cell to find the number of cells inside the label, step128. Then, at step 132, the center point of each cell used to find thenumber of cells both inside the label and inside the map.

The fraction of the label inside the map boundary is determined at step136. The high and the low values of the x and y coordinates for thevertices of the label are found in step 140. Then the label is tested,step 144, to determine if the fraction of the label inside the mapboundary is high enough to qualify for attempted movement inside themap. There is one of two possible ways the label might move depending onits movement constraints, which is determined in step 148. One movement,in both the x-axis and y-axis direction, is performed in steps 152, 156,160, 164, and 168. The other movement, restricted to a vector, isperformed in steps 172, 176, 180, 184, and 188. If the label ispartially or totally outside the map, and cannot be properly movedwithin the map, which is checked in step 192, then a parameter for thatlabel is set in step 196.

Once all labels have been tested, step 104 exits routine 10 and proceedsto routine 20.

Referring to FIG. 5, labels are sorted by priority at step 200 from thehighest priority label to the lowest priority label and placed into adata structure map. Step 210 exits routine 20 and proceeds to routine30, an initialization of halting criteria variables.

In FIG. 6, step 300 initializes halting criteria variables. Step 310exits routine 30 and proceeds to routine 40, a test of every combinationof two labels for overlap. Another expression for halting criteriavariables is collision scores and priority ranges, as shown in FIG. 10,step 590.

The above-described logic is further shown in the following pseudo-codewith comments: PULL IN THE LABELS FROM THE EDGES OF THE MAP ROUTINE//Pseudo-code for the Initialization of the Anti-collision Procedure forMaps //List of pseudo-code variables previous_collision_score - thecollision score from the previous iterationprevious_previous_collision_score - the collision score from twoiterations ago iteration_count - number of times the anti-collisionprocedure has looped slow_change_count - number of iterations ofcontinuous slow change of collision score oscillation_count - number ofiterations of continuous oscillation of collision scorepriority_of_most_important_label - numerical priority value of the mostimportant label priority_range - the difference between the priority ofthe least and the most important labels. This number is non-negative.frac_inside - fraction of label inside the map boundaries map_x_size -the number of x units in the map - map boundary is a rectanglemap_y_size - the number of y units in the map - map boundary is arectangle (xMove2D, yMove2D) - the label movement if the label qualifiesfor movement completely inside the map boundary and the label parametersspecify 2D type movement (xMoveVec[ ], yMoveVec[ ]) - an array of labelmovements if the label qualifies for movement completely inside the mapboundary and the label parameters specify vector type movement (xc,yc) - center point of a cell formed from a grid within thecircumscribing rectangle around the label (x_IP, y_IP) - a pointsatisfying various conditions used to properly move a label completelyinside the map boundary LABEL_TOO_MUCH_OUTSIDE_PORTRAIT - indicates ifthe procedure has determined that the label has much area outside themap boundary or can not be properly moved to a new position completelyinside the map boundary. This is a flag of every label set by theprocedure. LABEL_OUTSIDE_PORTRAIT - Not used. This is a flag of everylabel set by the procedure. LABEL_MOVED_INTO_PORTRAIT - indicates if theprocedure has moved a label that was originally partially outside themap boundary to a new position completely inside the map boundary. Thisis a flag of every label set by the procedure.LABEL_MIN_FRACTION_INSIDE - minimum fraction of the label that must beinside the map boundary to attempt relocation completely inside the mapboundary. This is a parameter of every label set by caller.LABEL_NEW_LOCATION - A vector (x, y) which is added to all vertices of alabel if the procedure moves the label. This vector has an initial valueof (0, 0). This is a parameter of every label determined by theprocedure. // pseudo-code also has: // a list of possible label movementcandidates to pull the label inside the map boundary // a data structuremap of labels and their properties sorted by priority from the most //important label to the least important label------------------------------------------------------------ // THIS ISTHE START OF ROUTINE 10 // The labels are not in any particular order atthis point. // They are only in the order in which they are receivedfrom the caller. for i = first unordered label to last unordered label set label i flag LABEL_OUTSIDE_PORTRAIT = FALSE  set label i flagLABEL_TOO_MUCH_OUTSIDE_PORTRAIT = FALSE  set label i flagLABEL_MOVED_INTO_PORTRAIT = FALSE  set label i parameterLABEL_NEW_LOCATION = (0, 0)  // Determine if the label is inside oroutside the map boundary.  // If all vertices are inside, then theentire label is inside.  // Here, a vertex on the map boundary is insidethe boundary.  label_inside_map = TRUE  for j = first vertex of label ito last vertex of label i  if ( vertex j outside map boundary ) {  label_inside_map = FALSE  }  next j  if ( label_inside_map = FALSE ) { // Below, find the approximate fraction of the label inside the mapboundary.  // The circumscribing rectangle has edges parallel to the mapedges.  // Note that both the rectangle and the label are convexpolygons.  Put a circumscribing rectangle around label i  Divide thecircumscribing rectangle into 64 units by 64 units forming 4096 cells in_label = 0  in_label_and_map = 0  for k = first cell to last cell  Find center point of cell k called (xc, yc)   // Here, a point on alabel edge or map boundary is inside the label or map.   // Use the“point inside convex polygon” procedure described in the   // labelsoverlap section.   if( (xc, yc) inside label ) {   in_label = in_label +1   if( (xc, yc) inside map boundary ) {    in_label_and_map =in_label_and_map + 1   }   }  next k  frac_inside = ( in_label_and_map)/( in_label )  // Move the label inside the map boundary if enough ofthe label is inside.  // Some of the vertices below may be the samevertex.  (x_low, yL) = coordinates of vertex with lowest x coordinate (x_high, yH) = coordinates of vertex with highest x coordinate  (xL,y_low) = coordinates of vertex with lowest y coordinate  (xH, y_high) =coordinates of vertex with highest y coordinate  // find the newlocation for the label  if ( frac_inside > LABEL_MIN_FRACTION_INSIDEparameter of label i ) {   if ( 2D type movement for label i ) {  (xMove2D, yMove2D) = (0, 0)   // If both conditions are true, thelabel will not fit into the map.   if ( x_low < 0 ) {    xMove2D = 0 −x_low   }   else if ( x_high > map_x_size − 1 ) {    xMove2D =map_x_size − 1 − x_high   }   // If both conditions are true, the labelwill not fit into the map.   if ( y_low < 0 ) {    yMove2D = 0 − y_low  }   else if ( y_high > map_y_size − 1 ) {    yMove2D = map_y_size − 1− y_high   }   // Determine if the label is still within its movementparameters.   // This means has the label moved too far from itsoriginal position.   // The original location parameter is neverchanged. It does not change   // because it is always used forcomparison to the new position.   if ( (xMove2D, yMove2D) within label i2D type movement parameters ) {    // Determine if the label is stillinside the map boundary after movement.    // This is really a test tosee if the label is too big to fit in the map.    // Here, a vertex onthe map boundary is not outside the map.    // This test works becauseboth label and map are convex polygons.    for j = first vertex of labeli to last vertex of label i    label_moved_outside_map = FALSE    if ( (vertex j + (xMove2D, yMove2D) ) of label i is outside map boundary ) {    label_moved_outside_map = TRUE    }    next j    if (label_moved_outside_map = FALSE ) {    set label i flagLABEL_MOVED_INTO_PORTRAIT = TRUE    set label i parameterLABEL_NEW_LOCATION = (xMove2D, yMove2D)    }   }   }   else { // vectortype movement   count = 0   // If both conditions are true, the labelwill not fit into the map.   if ( x_low < 0 ) {    find a point (x_IP,y_IP) which meets the following requirements    contained by a lineparallel to the vector type movement    contained by a the line x = 0   contained by a line also containing (x_low, yL)   if ( (x_IP, y_IP)exists ) {    xMoveVec[count] = x_IP − x_low    yMoveVec[count] = y_IP −yL    place in list of possible label movement candidates    count =count + 1   }   }   else if ( x_high > map_x_size − 1 ) {   find a point(x_IP, y_IP) which meets the following requirements    contained by aline parallel to the vector type movement    contained by a the line x =map_x_size − 1    contained by a line also containing (x_high, yH)   if( (x_IP, y_IP) exists ) {    xMoveVec[count] = x_IP − x_high   yMoveVec[count] = y_IP − yH    place in list of possible labelmovement candidates    count = count + 1   }   }  // If both conditionsare true, the label will not fit into the map.   if ( y_low < 0 ) {  find a point (x_IP, y_IP) which meets the following requirements   contained by a line parallel to the vector type movement    containedby a the line y = 0    contained by a line also containing (XL, y_low)  if ( (x_IP, y_IP) exists ) {    xMoveVec[count] = x_IP − xL   yMoveVec[count] = y_IP − y_low    place in list of possible labelmovement candidates    count = count + 1   }   }   else if ( y_high >map_y_size − 1 ) {   find a point (x_IP, y_IP) which meets the followingrequirements    contained by a line parallel to the vector type movement   contained by a the line y = map_y_size − 1    contained by a linealso containing (xH, y_high)   if ( (x_IP, y_IP) exists ) {   xMoveVec[count] = x_IP − xH    yMoveVec[count] = y_IP − y_high   place in list of possible label movement candidates    count =count + 1   }   }   // Can have zero, one, or two possible labelmovement candidates   for k = 0 to (count − 1)   // Determine if thelabel is still within its movement parameters.   // This means has thelabel moved too far from its original position.   // The originallocation parameter is never changed. It does not change   // because itis always used for comparison to the new position.   move_distance =magnitude of (xMoveVec[k], yMoveVec[k])   if ( move_distance withinlabel i vector type movement parameters ) {    // Determine if the labelis still inside the map boundary after movement.    // This is really atest to see if the label is too big to fit in the map.    // Here, avertex on the map boundary is not outside the map.    // This test worksbecause both label and map are convex polygons.    for j = first vertexof label i to last vertex of label i     label_moved_outside_map = FALSE    if(( vertex j + (xMoveVec[k], yMoveVec[k])) of label i is outsidemap boundary) {     label_moved_outside_map = TRUE     }    next j    if( label_moved_outside_map = FALSE ) {     set label i flagLABEL_MOVED_INTO_PORTRAIT = TRUE     set label i parameterLABEL_NEW_LOCATION = (xMoveVec[k], yMoveVec[k])     break out of loop //go past next k    }    }   next k   } // end of vector type movement  } if ( label i flag LABEL_MOVED_INTO_PORTRAIT = FALSE ) {   set label iflag LABEL_TOO_MUCH_OUTSIDE_PORTRAIT = TRUE  }  } // end iflabel_inside_map = FALSE next i // THIS IS THE START OF ROUTINE 20 //Sort the labels by priority. // The labels with the highest prioritieshave the lowest numbers. // Priorities may be negative numbers. //Labels may have the same priority. // After this loop, assume all labelsare ordered properly. Sort labels by priority from the most importantlabel to the least important label  and place into a data structure map// THIS IS THE START OF ROUTINE 30 // Initialize halting criteriavariables priority_range = priority_of_least_important_label −priority_of_most_important_label // initialize these two variables tolarge numbers previous_collision_score = Very Large Numberprevious_previous_collision_score = Very Large Number iteration_count =0 slow_change_count = 0 oscillation_count = 0

There is a process for comparing labels for overlap that is used severaltimes in this invention. A list of labels has been previously sorted inorder of priority, routine 20, where the highest priority label is firston the list. The order of labels with the same priority isinterchangeable with among themselves. Starting with the highestpriority label, it is compared against every label below it on the listfrom the second label to the last label in order of priority. Next,starting with the second highest priority label, it is compared againstevery label below it on the list from the third label to the last labelin order of priority. Continuing the process, label n is chosen andcompared to every label below it on the list from label n+1 to the lastlabel in order of priority, until the process is exhausted. In thismanner, every unique pair of labels is compared in order of priority.This process for the purposes of this application is termed cyclingthrough label pairs.

Referring to FIGS. 7 a and 7 b, labels are compared to determine if theyoverlap (routine 40). The number of labels and the maximum numericaldifference between the highest and lowest priority labels is determinedin step 400. All labels are grouped according to priority in steps 403,406, 409, and 412. It is important to choose the order of comparisonproperly to avoid excessive calculation and moving labels more timesthan necessary. Steps 415, 421, 424, 427, 430, 436, and 442 performcycling through label pairs. If either member of a unique pair obtainedby each iteration of the cycling will not be drawn on the map for anyreason, steps 433 and 439 continue to the next pair of labels avoidingunnecessary testing with the label that will not be used. Step 445,which corresponds to routine 45, tests for overlap between the membersof the pair. Step 448, which corresponds to routine 50, performs themovement procedure on one of the labels if they overlap. Step 418 exitsroutine 40 and proceeds to routine 60, an evaluation function procedure.

The above-described logic is further shown in the following pseudo-codewith comments: Order of Comparison for the Label Overlap Test Routine //The n labels have already been sorted in priority order, // from themost important, label 0, consecutively, // to the least important, label(n − 1). LABEL_TOO_MUCH_OUTSIDE_PORTRAIT - indicates if the procedurehas determined that the label has much area outside the map boundary orcan not be properly moved to a new position completely inside the mapboundary. This is a flag of every label set by the procedure.LABEL_OUTSIDE_PORTRAIT - Not used. This is a flag of every label set bythe procedure. LABEL_MOVED_INTO_PORTRAIT - indicates if the procedurehas moved a label that was originally partially outside the map boundaryto a new position completely inside the map boundary. This is a flag ofevery label set by the procedure. last_Label_Index = number_of_labels −1; // zero based // Zero based. // The highest priority is zero and thelowest priority is a number greater than zero. // Note that there may bepriorities which have no labels. last_Pri = lowest priority − highestpriority; // which equal the lowest priority // Below, if there are nolabels with priority p, // first_Pri[p] = −1 and last_Pri[p] = −1 //first_label[p] = first label index with priority p // last_label[p] =last label index with priority p for p = 0 to last_Pri; // highestpriority to lowest priority  if labels with priority p exist first_label[p] = most important label with priority p;  last_label[p] =least important label with priority p;  else  first_label[p] = −1; last_label[p] = −1; next p; for i_pri = 0 to last_Pri; // highestpriority to lowest priority  if first_label[i_pri] = −1, continue tonext i_pri;  for j_pri = i_pri to last_Pri; // highest priority tolowest priority  if first_label[j_pri] = −1, continue to next j_pri; for i_idx = first_label[i_pri] to last_label[i_pri];  if i_idx flag LABEL_TOO_MUCH_OUTSIDE_PORTRAIT = TRUE OR        LABEL_OUTSIDE_PORTRAIT = TRUE, continue to next i_idx   forj_idx = first_label[j_pri] to last_label[j_pri];   // Do not compare alabel to itself or   // compare labels which have been previouslycompared,   // for this particular iteration of the entire algorithm.  if i_idx <= j_idx, continue to next j_idx;   if j_idx flag LABEL_TOO_MUCH_OUTSIDE_PORTRAIT = TRUE OR        LABEL_OUTSIDE_PORTRAIT = TRUE, continue to next j_idx   if labeli_idx overlaps label j_idx,      then perform the label movementprocedure on label j_idx;   next j_idx;  next i_idx;  next j_pri; nexti_pri;

All labels are restricted to convex planar polygons in the plane of themap. A planar polygon is convex if it contains all the line segmentsconnecting any pair of its points. If two convex planar polygonsoverlap, this means that:

1) at least one vertex of one polygon is inside the other polygon, or

2) at least one edge of one polygon intersects an edge of the otherpolygon.

Routine 45, shown in FIG. 8, is a label overlap test procedure. Theoverlap test has three parts. First, it determines if any vertex of thefirst polygon is inside the second polygon, step 462. Second, itdetermines if any vertex of the second polygon is inside the firstpolygon, step 466. Third, it determines if any edge of the first polygonintersects any edge of the second polygon, step 470. Once any vertex isfound to be inside the other polygon, there is no need to test remainingvertices and edges. Once any edge is found to intersect any edge of theother polygon, there is no need to test remaining edges and vertices.

Prior to the overlap test, routine 45 begins by receiving two labelsfrom caller in step 450. In step 454, the maximum and minimum x and yvalues for each label are determined. These x and y values formcircumscribing rectangles, whose edges are parallel to the map's x axisand y axis, for each label. In step 458, the circumscribing rectanglesfor each label are compared. If these circumscribing rectangles do notoverlap, then routine 45 returns “no overlap” to the caller in step 478.

FIG. 8 shows the test for whether a vertex of a polygon is insideanother polygon. Consider the standard right-handed two-dimensionalCartesian coordinate system with the positive y direction up and thepositive x direction to the right. A first polygon's edges are chosensuch that the perimeter is traversed in the counterclockwise (CCW)direction (the perimeter may be traversed in a clockwise direction solong as it is done consistently). At step 462, if any vertex of a secondpolygon is to the left of all edges of the first polygon, then thatvertex is inside the first polygon. Likewise, at step 466, if any vertexof the first polygon is to the left of all edges of the second polygonthen that vertex is inside the second polygon. If any vertex of apolygon is inside another polygon, then the polygons overlap. This isthe test for a point being inside a convex planar polygon.

Lines containing the edges that make up a polygon may be written,(y−Y1)(X2−X1)−(x−X1)(Y2−Y1)=0where

-   (x,y) is any point on the line, and-   (X1,Y1) and (X2,Y2) are the endpoints of an edge of the polygon    under test. Points lying on the polygon edges satisfy the line    equations, while points not on the polygon edges do not satisfy    those equations. If (x, y) is any point in the plane, the equation    for a line containing an edge is:    (y−Y1)(X2−X1)−(x−X1)(Y2−Y1)=K    where K is a real number constant.

Then, for all points to the left of any edge, K>0, and for all points tothe right of any edge, K<0. Note that point 2 in the above equation isat the head of the vector representing the edge and point 1 is at thetail of the vector representing edge. This is true because, for alledges pointing to the right, (X2−X1)>0. For any point above the linecontaining the edge, (x_above, y_above), there exists a point, (x,y), onthe line, such that:x_above=x and y_above>yTherefore:(y−Y1)(X2−X1)−(x−X1)(Y2−Y1)=(y−Y1)(X2−X1)−(x−X1)(Y2−Y1)(y_above−Y1)(X2−X1)−(x−X1)(Y2−Y1)>(y−Y1)(X2−X1)−(x−X1)(Y2−Y1)(y_above−Y1)(X2−X1)−(x_above−X1)(Y2−Y1)>(y−Y1)(X2−X1)−(x−X1)(Y2−Y1)

A point that is above a line pointing to the right is a point that liesto the left of the line. Similar arguments show that any point on theleft of lines pointing up, pointing down, or pointing left yields apositive value with substituted into the line equation.

Step 470 tests whether the edges of one polygon intersect anotherpolygon. Consider the equations of the lines that contain the edges ofthe first polygon and the equations of the lines that contain the edgesof the second polygon. Determine the intersection point for everytwo-line combination, where one line is a line that contains an edge ofthe first polygon and the other line is a line that contains an edge ofthe second polygon. If the intersection point lies on or between theendpoints of the polygon edges, then the edge of one polygon intersectsthe edge of the other polygon and the polygons overlap. In cases wherethe lines are parallel, and not coincident, no intersection point existsfor that pair of lines. If the lines are coincident, then the edges mayor may not touch, but if the edges touch then the polygons overlap.

If the three above overlap tests, at step 462, step 466, step 470, findan overlap between the two labels, then routine 45 returns “labelsoverlap” to the caller in step 482, step 486, and step 490,respectively. If after performed the three tests, there is no overlapbetween the two labels, then routine 45 returns “no overlap” to thecaller in step 474.

The above-described logic is further shown in the following pseudo-codewith comments: Pseudo-code for the Overlap Test Of Convex PlanarPolygons List of pseudo-code variables (x_2_i, y_2_i) - vertex i ofpolygon 2 (X1_j, Y1_j) - vertex 1 of edge j of polygon 1 (X2_j, Y2_j) -vertex 2 of edge j of polygon 1 (x_IP, y_IP) - intersection point oflines containing edges x_max_i - max x of edge i y_min_j - min y on edgej find max x, max y, min x, min y on polygon 1 - each will be on avertex find max x, max y, min x, min y on polygon 2 - each will be on avertex // if any expression is true, the polygons do not overlap, soreturn false if (min x of polygon 1 >= max x of polygon 2) RETURNNO_OVERLAP if (min x of polygon 2 >= max x of polygon 1) RETURNNO_OVERLAP if (min y of polygon 1 >= max y of polygon 2) RETURNNO_OVERLAP if (min y of polygon 2 >= max y of polygon 1) RETURNNO_OVERLAP // if any vertex of polygon 2 is inside polygon 1, the resultis greater than zero. // proceed around polygon 1 in the CCW directionfor each vertex of polygon 2 for i = first vertex of polygon 2 to lastvertex of polygon 2  inside = TRUE  for j = first edge of polygon 1 tolast edge of polygon 1 in CCW direction  if((y_2_i − Y1_j) (X2_j − X1_j)− (x_2_i − X1_j) (Y2_j −  Y1_j) <= 0) inside = FALSE  next j  if (inside= TRUE), RETURN OVERLAP next i Repeat the above, except test polygon 1vertices with polygon 2 edges Return OVERLAP if appropriate // performthe edge intersection test for i = first edge of polygon 1 to last edgeof polygon 1  of the two endpoints of edge i, get x_max_i, y_max_i,x_min_i,  y_min_i  for j = first edge of polygon 2 to last edge ofpolygon 2  of the two endpoints of edge j, get x_max_j, y_max_j,x_min_j, y_min_j  solve for intersection point, (x_IP, y_IP), of linescontaining edge i and edge j  if intersection point exists   // Anintersection at an endpoint is an overlap.   // These tests also takecare vertical and horizontal edges.   if (x_IP <= x_max_i and x_IP >=x_min_i) and    (y_IP <= y_max_i and y_IP >= y_min_i) and    (x_IP <=x_max_j and x_IP >= x_min_j) and    (y_IP <= y_max_j and y_IP >=y_min_j), RETURN    OVERLAP  next j next i RETURN NO_OVERLAP

Labels must be moved about the map to clear existing label collisions.After it is determined that two labels overlap, routine 50 (FIGS. 9 a, 9b, and 9 c) finds several new locations for the lower priority of thetwo labels that eradicate the existing overlap. The higher prioritylabel is a first label while a lower priority label is a second label.These locations are ranked by how far the second label must be moved,shortest to longest. The actual location finally selected must meet thefollowing criteria:

-   -   1) the second label moves a shorter distance than other        qualifying locations;    -   2) the second label movement does not result in overlap with        another label (or labels) of equal or higher priority than the        first label;    -   3) the second label movement does not exceed the maximum        movement parameters for that particular label; and    -   4) no part of the second label is moved outside the map        boundary.

If no candidate locations meet these criteria, the second label is notmoved. During the process of fixing existing collisions, othercollisions may be created. New collisions are only allowed if it reducescollisions among labels with priorities equal to or higher than thefirst label. As the procedure iterates, new collisions are handled likethe original collisions. The procedure will minimize collisions.

Each label may be moved in one of two ways. A caller selects the type ofmovement of a label to the exclusion of the other type of movement.First, a label may move in any direction on the map, up to a maximumdistance from the original location. This is referred to as 2D typemovement. Second, a label may move parallel to a vector up to a maximumdistance from the original location in the positive vector direction orthe negative vector direction. This is referred to as vector typemovement that may be used for linear features such as highways andrivers. Both the vector and the maximum distances are in the label'sparameter list. Labels on a map may consist of any mixture of 2Dmovement and vector movement types. However, higher priority labels mustbe examined before lower priority labels regardless of movement type.

Prior to the attempted label movement, routine 50 begins by receivingtwo labels from caller in step 500. Routine 50 cycles through the edgesof first label in step 503 and cycles through the vertices of secondlabel in step 509. A counter is set in step 506. The first label's edgesare traversed in a CCW direction. Remembering that these operations takeplace on a two dimensional map, step 512 tests whether each vertex ofthe second label is left of a line containing an edge of the first labelwhen the first label is traversed in a CCW direction. A vertex of thesecond label is said to be on a label side of the line containing theedge of the first label if the vertex of the second label and area ofthe first label are on the same side of the line containing the edge ofthe first label. Note that these labels are restricted to convexpolygons so all of one label will be on one side of the line containingthe label's edge and no part of the label will be on the other side ofthe line. Likewise, a vertex of a second convex polygon is said to be ona convex polygon side of a line containing an edge of a first convexpolygon if the vertex of the second convex polygon and area of the firstconvex polygon are on the same side of the line containing the edge ofthe first convex polygon. If step 515 specifies a 2D type movement, thenstep 518 finds an intersection of two lines. A first line is the linethat contains one edge of the first label. A second line isperpendicular the first line and contains the vertex. If, instead, step515 specifies a vector type movement, then step 521 finds anintersection of a line containing an edge and a line parallel to thevector type movement also containing the vertex.

If in either the 2D type movement case or the vector type movement case,an intersection exists, step 524, and the vertex is on the label side asdefined above, step 527 calculates a first vector from the vertex to theintersection. If the first vector is too small, step 530, then theroutine 50 calculates, in steps 533, 536, and 539, a second vector withdesirable properties listed in steps 536 and 539. In the case that thefirst vector is too small, the first vector is replaced by the secondvector. Whichever vector remains, it is hereafter referred to as thevector.

Step 542 tests whether the vector is within movement bounds from theoriginal label location. If at step 545, it is within bounds, the vectoris placed on an end of a list of qualified vectors and a length of thevector is placed on an end of a length list. Once all vertices of thesecond label are tested, if there any qualified vectors (step 548),then, at step 551:

-   -   1) Find the maximum length in the length list and a        corresponding qualified vector from the vector list;    -   2) Insert the length and the qualified vector into a data        structure map that is sorted by distance; and    -   3) Empty the length list and vector list.

After all the edges of the first label are checked, at step 554 thesteps starting at step 512 are repeated using the edges of the secondlabel and the vertices of the first label. For any qualifying vectors, anegative of the vector is taken and that vector and its length areinserted into the data structure map.

Next, tests are performed to determine if proposed locations for thesecond label are acceptable. At step 560, starting with a shortestvector in the data structure map, the second label is moved in both adirection and a length of the shortest vector to obtain a new locationfor the second label. Then, at step 563, a test is performed todetermine if part of the new location for the second label is outsidethe map boundary. If, the new location for the second label places partof the second label outside the map boundary, repeat steps 557, 560, and563, using a next vector from the data structure map. Step 566 retrieveslabels with priorities greater than or equal to the first label. In step569, if any retrieved label is the first label or the second label, thenretrieve the next label in step 566. At step 572, the overlap test isperformed on the current candidate location for the second label againstlabels that fail tests at step 563 and step 569. If there is an overlap,steps 557 through 572 are repeated. Otherwise, the second label is movedto the candidate location in step 575. After a new location is found forthe second label among the proposed locations, or after all proposedlocations are determined to be unacceptable, then data structure map iscleared in step 578, and a next pair of labels is supplied in step 581.

The above-described logic is further shown in the following pseudo-codewith comments: Movement Procedure of Convex Planar Polygons // List ofpseudo-code variables (x_2_j, y_2_j) - vertex j of polygon 2 (X1_i,Y1_i) - vertex 1 of edge i of polygon 1 (X2_i, Y2_i) - vertex 2 of edgei of polygon 1 (x_IP, y_IP) - intersection point of lines containingedge and vertex (X,Y) - vector from vertex to edge pseudo-code also has: a list of distances  a list of vectors  a data structure map ofdistances and vectors sorted by distance, short to long // Polygon 1 isthe more important polygon and polygon 2 will move if possible // Here,the vertices in a polygon are on the left side of the edge // of theother polygon when traversing it in the CCW direction, // but thevertices are not necessarily inside the other polygon. // That is whyall possibilities are caught in the algorithm below - // even where novertex from either polygon is inside the other. // Do not have to checkspecifically for the above case. // If a vertex of polygon 2 is on leftside a polygon 1 edge, the result is greater than zero. // proceedaround polygon 1 in the CCW direction for each vertex of polygon 2 //Note the the vertex in question does not have to be inside polygon 1 fori = first edge of polygon 1 to last edge of polygon 1 in CCW direction count_of_possible_vertices = 0  for j = first vertex of polygon 2 tolast vertex of polygon 2  if((y_2_j − Y1_i)(X2_i − X1_i) − (x_2_j −X1_i)(Y2_i −  Y1_i) > 0)   if (2D type movement for polygon 2)   // asolution will always exist for this case   solve for intersection point,(x_IP, y_IP), of a line containing edge i   and a line perpendicular toedge i containing (x_2_j, y_2_j)   if (vector type movement for polygon2)   // a solution might not exist for this case   solve forintersection point, (x_IP, y_IP), of a line containing edge i   and aline parallel to the vector type movement containing (x_2_j, y_2_j)   if( solution exits for (x_IP, y_IP) )   // get vector from vertex tointersection point   (X,Y) = (x_IP − x_2_j, y_IP − y_2_j)   if ( (X,Y)length minute )    if ( 2D type movement for polygon 2 )     find apoint (X,Y) which meets the following requirements    on right side ofedge i (CCW)    contained by a line perpendicular to edge i    containedby a line also containing (x_IP, y_IP)    a minute distance from (x_IP,y_IP)    else // vector type movement for polygon 2     find a point(X,Y) which meets the following requirements    on right side of edge i(CCW)    contained by a line parallel to the vector type movement   contained by a line also containing (x_IP, y_IP)    a minute distancefrom (x_IP, y_IP)   // because polygon may move several times, keep theoriginal location of the label   if ( movement of (X,Y) leaves polygonwith movement limit )    // Make vector just a bit larger that thedistance to the edge    // so when polygon 2 is moved, it moves justoutside the polygon 1    length_of_XY = length of (X, Y) * (1.0 +1.0e−09)    X = X * (1.0 + 10e−09)    Y = Y * (1.0 + 10e−09)    appendlength_of_XY to end of distance list    append (X,Y) to end of vectorlist    count_of_possible_vertices = count_of_possible_vertices + 1 next j  if (count_of_possible_vertices > 0)   find the maximum distancein the distance list   get the corresponding vector to this distancefrom the vector list   insert the distance and the vector into the datastructure map sorted  by distance,   from the shortest distance to thelongest distance   empty distance list and vector list  next i  Repeatthe above, except use polygon 1 vertices and with polygon 2  edges  Thevector for possible movement, (X,Y), is reversed  Insert the resultsinto the same distance/vector data structure map  // the outer loop isjust going thought the sorted data structure map  for i = first locationcandidate to last location candidate   get new location for polygon byadding vector (X,Y) to each vertex   if ( any part of label outside mapboundary ) next i   for j = first label to last label whose priority >=polygon 1    if ( polygon 1 is label j or polygon 2 is label j) next j   if ( polygon 2 in location candidate i overlaps label j ) next i   update polygon 2 location in its parameter list    break out of bothfor loops   next j  next i  clear the data structure map  get the nextpair of labels to be tested for overlapThe Evaluation Function, the Halting Criteria, and the Adjustment ofLabel Properties

It is probable that the process of label movement will iterateindefinitely, therefore halting criteria are needed. An evaluationfunction provides input to a halting procedure to stop the process at anacceptable point. The calculation of the evaluation function isrepresented by FIG. 11. All labels that overlap are known at this point.The procedure used to reduce label collisions is an iterative process. Acollision score is a variable that measures the severity of collisionsof labels in the map. It is initialized to zero in step 600. Step 605performs cycling through label pairs. In step 610, each label of thecurrent pair of labels is tested to see if it has too much of its areais outside the map or if it is completely outside the map. This avoidsunnecessary calculation for labels that will not be used. The overlaptest (routine 45) is performed in step 615. If no overlap occurs betweenthe two labels being tested, then another unique pair of labels isfetched in step 605. If overlap occurs, then the collision score isadded to the previous collision score in step 620. The final value ofthe collision score is attained after all the unique label pairs havebeen tested. In this anti-collision procedure for maps, the evaluationfunction at step 620 is:${{Collision}\quad{Score}} = {\sum\limits_{ij}\begin{pmatrix}{\left( {{label}\quad i\quad{adjusted}\quad{priority}} \right)^{2} +} \\\left( {{label}\quad j\quad{adjusted}\quad{priority}} \right)^{2}\end{pmatrix}}$where the score is the summation over every pair of overlapping labels.The result of this function is defined as zero if no collisions remainand greater than zero if any collisions remain. The function penalizesdisproportionately for collisions involving high priority labels. Forinstance, a collision involving a high priority label and a low prioritylabel gets a higher score (worse) than a collision involving two mediumpriority labels.

Routine 70 as shown in FIG. 12 evaluates halting criteria to determineif the labels are in optimal locations. The iterative process must haltat some point. A slow change halting criteria is evaluated in step 700.If the slow change per iteration in the collision score occurs, the slowchange count is incremented by one in step 705. If the slow change periteration does not occur, the slow change variable is reset to zero instep 710. A short-term oscillation halting criteria is evaluated in step715. If the short-term oscillation in the collision score occurs, theshort-term oscillation count is incremented by one in step 720. If theshort-term oscillation does not occur, the short-term oscillation countis reset to zero in step 725. The previous values of the collision scoreare stored in step 730. Step 730 also increments the iteration count byone. Here, an iteration is one cycle of the anti-collision algorithmthat includes routines 40, 45, 50, and 60. Example rules tested at step735 to halt the procedure follow:

-   -   1) the evaluation function is below a minimum value;    -   2) the number of iterations is greater than a maximum value;    -   3) the evaluation function changes less than a minimum        percentage of the previous iteration for more than a set number        of iterations; and    -   4) the evaluation function oscillates for more than a set number        of consecutive iterations.

If none of these conditions are meet, the anti-collision algorithm isrepeated in step 740, noting that labels may move several times beforethe iterations stop. A label's new position is stored in its parameterlist at the time a label is moved. The original position is alwaysavailable in the label's parameter list.

Routine 80, as shown in FIG. 13, adjusts label properties. At thispoint, labels will not be moved because the halting criteria have beensatisfied. However, some labels may still overlap. Routine 80 begins instep 800 by setting the DRAW flag to TRUE for every label. Step 805cycles through all unique pairs of labels. In step 810, each label ofthe current pair of labels is tested to see if it has too much of itsarea is outside the map or if it is completely outside the map. Thisavoids unnecessary calculation for labels that are not used. Labels thathave some or all of their area outside the map have their DRAW flag setto FALSE in step 815. The overlap test (routine 45) is performed in step820 on those label pairs for which neither have any area outside themap. If no overlap occurs between the two labels being tested, thenanother unique pair of labels is fetched in step 805. If overlap occurs,then the MUST DRAW flags for both labels are examined in steps 825, 830,and 835. Depending on the result of this examination, the DRAW flag forone of the current labels is set to FALSE in step 840 and step 845.These flags are in the label's parameter list. The MUST DRAW flag is setby the caller. If the DRAW flag is true, this procedure will draw thelabel. If the DRAW is false, this procedure will not draw the label. Forany pair of overlapping labels, the following somewhat arbitrary rulesdetermine the final state of a label's DRAW flag:

-   -   1) If one label has MUST DRAW=TRUE, that label sets DRAW=TRUE,        and the second label sets DRAW=FALSE.    -   2) If both labels have MUST DRAW=TRUE, the label higher on the        list of label priority sets DRAW=TRUE, and the other label sets        DRAW=FALSE. Note that this will hold for labels of equal        priority.    -   3) If neither label has MUST DRAW=TRUE, the label higher on the        list of label priority sets DRAW=TRUE, and the other label sets        DRAW=FALSE. Note that this will hold for labels of equal        priority.

The label priority list and the overlap test are described in precedingsections of the description of the entire anti-collision procedure.

After label properties are adjusted, control is returned to the caller;in step 900 of FIG. 14.

The above-described logic is further shown in the following pseudo-codewith comments.

Pseudo-Code for the Evaluation Function, the Halting Criteria, and theAdjustment of Label Properties List of pseudo-code variablescollision_score - the sum of the evaluation function after eachiteration previous_collision_score - the collision score from theprevious iteration previous_previous_collision_score - the collisionscore from two iterations ago iteration_count - number of times theanti-collision procedure has looped slow_change_count - number ofiterations of continuous slow change of collision scoreoscillation_count - number of iterations of continuous oscillation ofcollision score priority_of_most_important_label - numerical priorityvalue of the most important label priority_range - the differencebetween the priority of the least and the most important labels. Thisnumber is non-negative. adjusted_priority_1 - the label 1 prioritymodified to make it work in the evaluation function // EvaluationFunction ----------------------------------------------- collision_score= 0 // these loops go thought label priority list for i = first label tolast label  if( label i flag LABEL_TOO_MUCH_OUTSIDE_PORTRAIT = TRUE OR   label i flag LABEL_OUTSIDE_PORTRAIT = TRUE ) next i  for j = labeli+1 to last label  if( label j flag LABEL_TOO_MUCH_OUTSIDE_PORTRAIT =TRUE OR    label j flag LABEL_OUTSIDE_PORTRAIT = TRUE ) next j  if(label i and label j overlap )  {   // Adjust the label priorities tomake the evaluation function work properly.   // Note that the highestpriority labels are assigned the lowest numbers and   // priorities maybe positive or negative.   adjusted_priority_1 = 1 + priority_range −            ( label_1_priority − priority_of_most_important_label )  adjusted_priority_2 = 1 + priority_range −             (label_2_priority − priority_of_most_important_label )   collision_score= collision_score +            (adjusted_priority_1)*(adjusted_priority_1) +            (adjusted_priority_2)*(adjusted_priority_2)  }  next j nexti // Halting Algorithm --------------------------------------- // isthere slow change ? if(collision_score <= previous_collision_score AND  collision_score > 0.98*previous_collision_score) {  slow_change_count= slow_change_count + 1 } else {  slow_change_count = 0 } // is thereoscillation ? if( (collision_score > previous_collision_score AND  previous_collision_score < previous_previous_collision_score ) OR  (collision_score < previous_collision_score AND  previous_collision_score > previous_previous_collision_score ) ) { oscillation_count = oscillation_count + 1 } else {  oscillation_count =0 } iteration_count = iteration_count + 1previous_previous_collision_score = previous_collision_scoreprevious_collision_score = collision_score if(collision_score = 0) gotoADJUST_LABEL_PARAMETERS if(iteration_count > 20) gotoADJUST_LABEL_PARAMETERS if(slow_change_count > 4) gotoADJUST_LABEL_PARAMETERS if(oscillation_count > 6) gotoADJUST_LABEL_PARAMETERS goto Start of Next IterationADJUST_LABEL_PARAMETERS: //-------------------------------------------// set label flag DRAW = TRUE for all labels for i = first label to lastlabel  label_i_DRAW = TRUE next i // these loops go thought labelpriority list and set the draw flag for i = first label to last label if( label i flag LABEL_TOO_MUCH_OUTSIDE_PORTRAIT = TRUE OR    label iflag LABEL_OUTSIDE_PORTRAIT = TRUE )  {  label_i_DRAW = FALSE  next i  } for j = label i+1 to last label  if( label j flagLABEL_TOO_MUCH_OUTSIDE_PORTRAIT = TRUE OR    label j flagLABEL_OUTSIDE_PORTRAIT = TRUE )  {   label_j_DRAW = FALSE   next j  } if( label i and label j overlap )  {   if ( label_i_MUST_DRAW = TRUEAND label_j_MUST_DRAW = TRUE )   {   label_j_DRAW = FALSE   }   else if( label_i_MUST_DRAW = TRUE )   {   label_j_DRAW = FALSE   }   else if (label_j_MUST_DRAW = TRUE )   {   label_i_DRAW = FALSE   }   else   { label_j_DRAW = FALSE   }  }  next j next i return to caller

While the particular SYSTEM AND METHOD FOR LABELING MAPS as herein shownand described in detail is fully capable of attaining theabove-described objects of the invention, it is to be understood that itis the presently preferred embodiment of the present invention and isthus representative of the subject matter which is broadly contemplatedby the present invention, that the scope of the present invention fullyencompasses other embodiments which may become obvious to those skilledin the art, and that the scope of the present invention is accordinglyto be limited by nothing other than the appended claims, in whichreference to an element in the singular means “at least one”. Allstructural and functional equivalents to the elements of theabove-described preferred embodiment that are known or later come to beknown to those of ordinary skill in the art are expressly incorporatedherein by reference and are intended to be encompassed by the presentclaims. Moreover, it is not necessary for a device or method to addresseach and every problem sought to be solved by the present invention, forit to be encompassed by the present claims. Furthermore, no element,component, or method step in the present disclosure is intended to bededicated to the public regardless of whether the element, component, ormethod step is explicitly recited in the claims.

1. A method for placing labels on a map comprising: retrieving eachlabel's association with a respective target feature on the map withoutregard to other labels or features, retrieving map features' properties,retrieving labels' properties, pulling labels within map boundaries,ordering labels in rank of descending priority, initializing haltingcriteria variables, testing each label in turn for overlap with otherlabels, moving labels, which overlap other labels, to locations wherethere is no overlap, or where there is overlap with one or more labelsof lesser priority, eliminating labels which cannot be placed on the mapwithout overlapping other labels, calculating an evaluation function,determining if movement of labels is to be halted, and adjusting labelproperties.
 2. A method for placing labels on a map comprising thefollowing steps: retrieving each label's association with a respectivetarget feature on the map without regard to other labels or features,retrieving map features' properties, retrieving labels' properties,pulling labels within map boundaries, ordering labels in rank ofdescending priority, initializing halting criteria variables, theniterating a procedure wherein the procedure comprises: a. determining ifall unique label pairs have been tested, and if all label pairs havebeen tested proceeding to step d, b. cycling through label pairs,testing whether pair members overlap each other, and, if the members donot overlap, then proceeding to step a, c. moving a second member of thelabel pair to a location where there is no overlap with any label, or toa location where there is overlap with one or more labels of lesserpriority than a first label of the label pair, and proceeding to step a,d. calculating an evaluation function, e. determining if the proceduremust be halted, and if the procedure is not halted, proceeding to stepa, adjusting label properties, and returning to caller.
 3. The method ofclaim 1 wherein the pulling labels within map boundaries comprises:determining whether each label is wholly within the map boundaries,determining, for labels not wholly within map boundaries, what fractionof each label area is within the map boundaries, and moving the labelwithin the map boundaries, if the fraction of a label area outside themap boundaries is less than a predetermined value.
 4. The method ofclaim 2 wherein the pulling labels within map boundaries comprises:determining whether each label is wholly within the map boundaries,determining, for labels not wholly within map boundaries, what fractionof each label area is within the map boundaries, and moving the labelwithin the map boundaries, if the fraction of a label area outside themap boundaries is less than a predetermined value.
 5. The method ofclaim 1 wherein initializing halting criteria variables comprises:initializing variables for previous collision score, prior previouscollision score, iteration count, slow change count, and oscillationcount.
 6. The method of claim 2 wherein initializing halting criteriavariables comprises: initializing variables for previous collisionscore, prior previous collision score, iteration count, slow changecount, and oscillation count.
 7. The method of claim 1 wherein thetesting of each label in turn for overlap with other labels comprises:choosing a first and second label to compare, associating the firstlabel with a region of a first convex planar polygon, associating thesecond label with a region of a second convex planar polygon, findingmaximum extents of the first and second convex planar polygonsrespectively associated with the first and second labels, comparing themaximum extent of the first polygon with the maximum extent of thesecond polygon and, if the extents do not overlap, concluding that thefirst and second labels do not overlap, testing vertices of the firstpolygon with edges forming a perimeter of the second polygon and, if anyvertex is within the second polygon, concluding that the labels overlap,testing each edge of the first polygon with each edge of the secondpolygon, and, if any of the edges being tested intersect, and thenconcluding that the labels overlap, and repeating the steps for testingof each label for overlap with other labels until all labels are testedagainst all other labels.
 8. The method of claim 2 wherein the testingof each label in turn for overlap with other labels comprises: choosinga first and second label to compare, associating the first label with aregion of a first convex planar polygon, associating the second labelwith a region of a second convex planar polygon, finding maximum extentsof the first and second convex planar polygons respectively associatedwith the first and second labels, comparing the maximum extent of thefirst polygon with the maximum extent of the second polygon and, if theextents do not overlap, concluding that the first and second labels donot overlap, testing vertices of the first polygon with edges forming aperimeter of the second polygon and, if any vertex is within the secondpolygon, concluding that the labels overlap, testing each edge of thefirst polygon with each edge of the second polygon, and, if any of theedges being tested intersect, and then concluding that the labelsoverlap, and repeating the steps for testing of each label for overlapwith other labels until all labels are tested against all other labels.9. The method of claim 7 wherein testing vertices of the first polygonwith edges forming a perimeter of the second polygon comprises:traversing the perimeter of the second polygon, obtaining equations ofthe lines containing edges of the second polygon, testing vertices ofthe first polygon with the equations of the lines containing edges ofthe second polygon until all vertices of the first polygon are tested,and concluding that the labels overlap if any vertex of the firstpolygon is within the boundary of the second polygon as determined bythe equations.
 10. The method of claim 8 wherein testing vertices of thefirst polygon with edges forming a perimeter of the second polygoncomprises: traversing the perimeter of the second polygon, obtainingequations of the lines containing edges of the second polygon, testingvertices of the first polygon with the equations of the lines containingedges of the second polygon until all vertices of the first polygon aretested, and concluding that the labels overlap if any vertex of thefirst polygon is within the boundary of the second polygon as determinedby the equations.
 11. The method of claim 7 wherein testing edges of thefirst polygon with edges of the second polygon comprises: obtainingequations of lines containing edges of the first polygon, obtainingequations of lines containing edges of the second polygon, calculatingintersection points of the edges of the first polygon and the edges ofthe second polygon, determining if the points lie on any of the edges ofthe first polygon or any of the edges of the second polygon, andconcluding that if at least one of the points lies on any of the edgesof the first polygon or any of the edges of the second polygon then thelabels overlap.
 12. The method of claim 8 wherein testing edges of thefirst polygon with edges of the second polygon comprise: obtainingequations of lines containing edges of the first polygon, obtainingequations of lines containing edges of the second polygon, calculatingintersection points of the edges of the first polygon and the edges ofthe second polygon, determining if the points lie on any of the edges ofthe first polygon or any of the edges of the second polygon, andconcluding that if at least one of the points lies on any of the edgesof the first polygon or any of the edges of the second polygon then thelabels overlap.
 13. The method of claim 1 wherein calculating theevaluation function comprises: setting current collision score to zero,cycling through label pairs, testing whether the members of the currentlabel pair overlap, checking whether either label of the pair is too faroutside or completely outside the map boundary, calculating a collisionscore of label overlap, calculating a slow change count, calculating anoscillation count, and updating iteration count.
 14. The method of claim2 wherein calculating the evaluation function comprises: setting currentcollision score to zero, cycling through label pairs, testing whetherthe members of the current label pair overlap, checking whether eitherlabel of the pair is too far outside or completely outside the mapboundary, calculating a collision score of label overlap, calculating aslow change count, calculating an oscillation count, and updatingiteration count.
 15. The method of claim 13 wherein determining ifmovement of labels is to be halted comprises: testing if: a. thecollision score of label overlap is zero, or b. the slow change countexceeds maximum number, or c. the oscillation count exceeds a maximumnumber, or d. the iteration count exceeds a maximum number.
 16. Themethod of claim 14 wherein determining if the procedure must be haltedcomprises: testing if: a. the collision score of label overlap is zero,or b. the slow change count exceeds maximum number, or c. theoscillation count exceeds a maximum number, or d. the iteration countexceeds a maximum number.
 17. The method of claim 1 wherein adjustinglabel properties comprises cycling through label pairs, testing whetherpair members overlap each other, eliminating the second member of thelabel pair if it overlaps the first member of the label pair, andeliminating labels not pulled into the map boundaries.
 18. The method ofclaim 2 wherein adjusting label properties comprises cycling throughlabel pairs, testing whether pair members overlap each other,eliminating the second member of the label pair if it overlaps the firstmember of the label pair, and eliminating labels not pulled into the mapboundaries.
 19. A computer system for automatically labeling a map inaccordance with predefined label positioning and placement criteria, themap including a plurality of regions encompassing points with saidregion and bounded by region boundary points to be labeled with acorresponding label in accordance with said label positioning andplacement criteria, said system comprising: a. input means for inputtingmap data including region data for said plurality of regions to belabeled and label data including said corresponding label for each ofsaid plurality of regions, b. first memory means for storing said mapdata and said region data, c. processor means responsive to a controlprogram for generating digital signals corresponding to approximatelabel positions for each of said regions satisfying said labelpositioning criteria and digital signals denoting final label positionsfor each of said locations satisfying said label placement criteria,said processor means being adapted to: pulling qualifying labels withinthe map, ordering labels according to priority, initializing haltingcriteria variables, testing labels for overlap, moving overlappinglabels, calculating an evaluation function, executing a halt routine,and adjusting label properties, and d. output means for forwarding finallabel positions to a caller.
 20. A computer system for automaticallylabeling a map in accordance with predefined label positioning andplacement criteria, the map including a plurality of regionsencompassing points with said region and bounded by region boundarypoints to be labeled with a corresponding label in accordance with saidlabel positioning and placement criteria, said system comprising: inputmeans for inputting map data including region data for said plurality ofregions to be labeled and label data including said corresponding labelfor each of said plurality of regions, first memory means for storingsaid map data and said region data, processor means responsive to acontrol program for generating digital signals corresponding toapproximate label positions for each of said regions satisfying saidlabel positioning criteria and digital signals denoting final labelpositions for each of said locations satisfying said label placementcriteria, said processor means being adapted to executing the followinginstructions in sequence: retrieving each label's association with arespective target feature on the map without regard to other labels orfeatures, retrieving map features' properties, retrieving labels'properties, pulling qualifying labels within the map, ordering labels inrank of descending priority, initializing halting criteria variables,iterating procedure wherein the procedure comprises: a. determining ifall unique label pairs have been tested, and if all label pairs havebeen tested proceeding to step d, b. cycling through label pairs,testing whether pair members overlap each other, and, if the members donot overlap, then proceeding to step a, c. moving a second member of thelabel pair to a location where there is no overlap with any label, or toa location where there is overlap with one or more labels of lesserpriority than a first label of the label pair, and proceeding to step a,d. calculating an evaluation function, e. determining if the iteratingprocedure must be halted, and if the iterating procedure is not halted,then proceeding to step a, adjusting label properties, wherein adjustinglabel properties includes cycling through label pairs, testing whetherpair members overlap each other, eliminating the second member of thelabel pair if it overlaps the first member of the label pair, andeliminating labels not pulled into the map boundaries, and output meansfor forwarding final label positions to a caller.
 21. A computer systemas claimed in claim 19, further comprising display means for displayinga graphic image of said map data together with a graphic image generatedfrom said digital signals corresponding to the final label positions ofeach label.
 22. A computer system as claimed in claim 20, furthercomprising display means for displaying a graphic image of said map datatogether with a graphic image generated from said digital signalscorresponding to the final label positions of each label.
 23. A computerstorage medium storing computer executable instructions for performingthe method of claim
 1. 24. A computer storage medium storing computerexecutable instructions for performing the method of claim 2.